Initialization data memory space allocation system

ABSTRACT

An initialization data memory space allocation system includes a memory system having a memory space that includes an initialization data bucket that reserves a contiguous subset of the memory space for initialization data. Each initialization engine that is coupled to the memory system is configured during initialization operations to allocate, for that initialization engine, a portion of the contiguous subset of the memory space reserved by the initialization data bucket, and then store initialization data in that portion of the contiguous subset of the memory space reserved by the initialization data bucket. A runtime engine that is coupled to the memory system is configured, during runtime operations, to claim the contiguous subset of the memory space reserved for initialization data by the initialization data bucket for runtime data, and store runtime data in at least a portion of the contiguous subset of the memory space.

BACKGROUND

The present disclosure relates generally to information handlingsystems, and more particularly to allocating memory space in aninformation handling system for initialization data.

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option available to users is information handling systems. Aninformation handling system generally processes, compiles, stores,and/or communicates information or data for business, personal, or otherpurposes thereby allowing users to take advantage of the value of theinformation. Because technology and information handling needs andrequirements vary between different users or applications, informationhandling systems may also vary regarding what information is handled,how the information is handled, how much information is processed,stored, or communicated, and how quickly and efficiently the informationmay be processed, stored, or communicated. The variations in informationhandling systems allow for information handling systems to be general orconfigured for a specific user or specific use such as financialtransaction processing, airline reservations, enterprise data storage,or global communications. In addition, information handling systems mayinclude a variety of hardware and software components that may beconfigured to process, store, and communicate information and mayinclude one or more computer systems, data storage systems, andnetworking systems.

Information handling systems such as, for example, server devices and/orother computing devices known in the art, perform initializationoperations in order to initialize the computing device so that thecomputing device may enter a runtime environment. During theinitialization operations discussed above, memory space in the mainmemory system (e.g., Dynamic Random Access Memory (DRAM) devices) may beallocated for the Basic Input/Output System (BIOS) and/or firmwaredrivers (e.g., UEFI firmware drivers) for use during initialization ofthe computing device. However, as would be understood by one of skill inthe art in possession of the present disclosure, memory space allocatedby the BIOS and/or firmware drivers during initialization may becomefragmented due to a variety of reasons. For example, a firmware drivermay be allocated a contiguous region or range of the memory space (e.g.,adjacent memory blocks in the memory space) during initialization and,when that firmware driver is finished utilizing that contiguous regionof the memory space, the firmware driver may only release some of thememory blocks in that contiguous region of the memory space (e.g., the“middle” memory blocks bounded on each side by memory blocks that arenot released by that firmware driver.) Thus, when another firmwaredriver attempts to allocate a contiguous region of the memory space,those released memory block(s) will not be used for that allocation.

Repeated situations like that discussed above create a fragmented memoryspace, which can lead to reduced computing device performance due to,for example, the need for firmware drivers to review relatively largeamounts of available memory space to find a contiguous region of thememory space for allocation, and the possibility that no contiguousregion of the memory space exists that satisfies the allocationrequirements for a firmware driver. Furthermore, such fragmented memoryspaces can expose bugs in firmware drivers. For example, relatively highlevels of fragmentation may require the processing system (e.g., aDirect eXecution Environment (DXE) core in the processing system) to usea relatively large number of descriptors in a memory map to identify thememory space to the Operating System (OS) in the computing device, whichhas been found to produced unexpected behavior with some OSs due to, forexample, limitations in their OS loader code.

Accordingly, it would be desirable to provide an initialization datamemory space allocation system that addresses the issues discussedabove.

SUMMARY

According to one embodiment, an Information Handling System (IHS)includes a processing system that is configured to: define aninitialization data bucket that reserves a contiguous subset of a memoryspace provided by a memory system for initialization data; and executeinstructions to cause the processing system to provide: at least oneinitialization engine, wherein each initialization engine is configured,during initialization operations, to: allocate, for that initializationengine, a portion of the contiguous subset of the memory space reservedby the initialization data bucket; and store initialization data in thatportion of the contiguous subset of the memory space reserved by theinitialization data bucket; and a runtime engine that is coupled to thememory system and that is configured, during runtime operations, to:claim the contiguous subset of the memory space reserved forinitialization data by the initialization data bucket for runtime data;and store runtime data in at least a portion of the contiguous subset ofthe memory space.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic view illustrating an embodiment of an InformationHandling System (IHS).

FIG. 2 is a schematic view illustrating an embodiment of a computingdevice that provides the initialization data memory space allocationsystem of the present disclosure.

FIG. 3 is a flow chart illustrating an embodiment of a method forallocating memory space for initialization data.

FIG. 4 is a schematic view illustrating an embodiment of the computingdevice of FIG. 2 operating during the method of FIG. 3.

FIG. 5 is a schematic view illustrating an embodiment of the computingdevice of FIG. 2 operating during the method of FIG. 3.

FIG. 6A is a schematic view illustrating an embodiment of a memorysystem in the computing device of FIG. 2 during the method of FIG. 3.

FIG. 6B is a schematic view illustrating an embodiment of a memorysystem in the computing device of FIG. 2 during the method of FIG. 3.

FIG. 7 is a schematic view illustrating an embodiment of the computingdevice of FIG. 2 operating during the method of FIG. 3.

FIG. 8 is a schematic view illustrating an embodiment of the computingdevice of FIG. 2 operating during the method of FIG. 3.

FIG. 9 is a schematic view illustrating an embodiment of the computingdevice of FIG. 2 operating during the method of FIG. 3.

FIG. 10 is a schematic view illustrating an embodiment of the computingdevice of FIG. 2 operating during the method of FIG. 3.

FIG. 11 is a schematic view illustrating an embodiment of the computingdevice of FIG. 2 operating during the method of FIG. 3.

FIG. 12 is a schematic view illustrating an embodiment of the computingdevice of FIG. 2 operating during the method of FIG. 3.

DETAILED DESCRIPTION

For purposes of this disclosure, an information handling system mayinclude any instrumentality or aggregate of instrumentalities operableto compute, calculate, determine, classify, process, transmit, receive,retrieve, originate, switch, store, display, communicate, manifest,detect, record, reproduce, handle, or utilize any form of information,intelligence, or data for business, scientific, control, or otherpurposes. For example, an information handling system may be a personalcomputer (e.g., desktop or laptop), tablet computer, mobile device(e.g., personal digital assistant (PDA) or smart phone), server (e.g.,blade server or rack server), a network storage device, or any othersuitable device and may vary in size, shape, performance, functionality,and price. The information handling system may include random accessmemory (RAM), one or more processing resources such as a centralprocessing unit (CPU) or hardware or software control logic, ROM, and/orother types of nonvolatile memory. Additional components of theinformation handling system may include one or more disk drives, one ormore network ports for communicating with external devices as well asvarious input and output (I/O) devices, such as a keyboard, a mouse,touchscreen and/or a video display. The information handling system mayalso include one or more buses operable to transmit communicationsbetween the various hardware components.

In one embodiment, IHS 100, FIG. 1, includes a processor 102, which isconnected to a bus 104. Bus 104 serves as a connection between processor102 and other components of IHS 100. An input device 106 is coupled toprocessor 102 to provide input to processor 102. Examples of inputdevices may include keyboards, touchscreens, pointing devices such asmouses, trackballs, and trackpads, and/or a variety of other inputdevices known in the art. Programs and data are stored on a mass storagedevice 108, which is coupled to processor 102. Examples of mass storagedevices may include hard discs, optical disks, magneto-optical discs,solid-state storage devices, and/or a variety other mass storage devicesknown in the art. IHS 100 further includes a display 110, which iscoupled to processor 102 by a video controller 112. A system memory 114is coupled to processor 102 to provide the processor with fast storageto facilitate execution of computer programs by processor 102. Examplesof system memory may include random access memory (RAM) devices such asdynamic RAM (DRAM), synchronous DRAM (SDRAM), solid state memorydevices, and/or a variety of other memory devices known in the art. Inan embodiment, a chassis 116 houses some or all of the components of IHS100. It should be understood that other buses and intermediate circuitscan be deployed between the components described above and processor 102to facilitate interconnection between the components and the processor102.

Referring now to FIG. 2, an embodiment of a computing device 200 isillustrated that may provide the initialization data memory spaceallocation system of the present disclosure. In an embodiment, thecomputing device 200 may be provided by the IHS 100 discussed above withreference to FIG. 1 and/or may include some or all of the components ofthe IHS 100, and in specific examples may be provided by a serverdevice, a desktop computing device, a laptop/notebook computing device,a tablet computing device, a mobile phone, and/or other computingdevices that would be apparent to one of skill in the art in possessionof the present disclosure. Furthermore, while one of skill in the art inpossession of the present disclosure will recognize that the computingdevice 200 is illustrated and discussed below as being provided byserver device, the functionality of the computing device 200 discussedbelow may be provided by other devices that are configured to operatesimilarly as computing device 200 discussed below. In the illustratedembodiment, the computing device 200 includes a chassis 202 that housesthe components of the computing device 200, only some of which areillustrated below.

For example, the chassis 202 may house a processing system 204 (e.g.,that may include the processor 102 discussed above with reference toFIG. 1) that, in some of the embodiments discussed below, may includeprocessing subsystem(s) such as the High Bandwidth Memory (HBM) systemillustrated in FIG. 2, which one of skill in the art in possession ofthe present disclosure will appreciate may be included in processingsystems available from ADVANCED MICRO DEVICES® Inc. of Santa Clara,Calif., United States. However, one of skill in the art in possession ofthe present disclosure will appreciate that some of the embodimentsbelow do not utilize the HBM system 204 a, and thus its inclusion withthe processing system 204 may be optional. Furthermore, in addition tothe optional HBM system 204 a, the processing system 204 may includeother processing subsystems such as the Driver eXecution Environment(DXE) core discussed below, other processing systems cores known in theart, a chipset, and/or any other processing subsystems that one of skillin the art in possession of the present disclosure would recognize thatbeing capable of providing the BIOS sub-engine(s), operating systemsub-engine, and/or other processing system functionality discussedbelow.

The chassis 202 may also house a main memory system 206 that is coupledto the processing system 206 and that may be provided by Dynamic RandomAccess Memory (DRAM) devices and/or other main memory subsystems thatwould be apparent to one of skill in the art in possession of thepresent disclosure. However, while two specific memory systems areillustrated and described in FIG. 2, one of skill in the art inpossession of the present disclosure will recognize that other memorysystems may be utilized in place of those illustrated in FIG. 2 whileremaining within the scope of the present disclosure as well.Furthermore, while a specific computing device 200 has been illustrated,one of skill in the art in possession of the present disclosure willrecognize that computing devices (or other devices operating accordingto the teachings of the present disclosure in a manner similar to thatdescribed below for the computing device 200) may include a variety ofcomponents and/or component configurations for providing conventionalcomputing device functionality, as well as the functionality discussedbelow, while remaining within the scope of the present disclosure aswell.

Referring now to FIG. 3, an embodiment of a method 300 for allocatingmemory space for initialization data is illustrated. As discussed below,the systems and methods of the present disclosure provide for thecreation of an initialization data bucket that reserves a subset of thememory space provided by a memory system in a computing device forinitialization data, and then the allocation of portions of that subsetof the memory space for initialization engines in the computing device,and the use of those portions of that subset of the memory space by theinitialization engines for which they were allocated in order to storeinitialization data during initialization operations. Upon thecompletion of the initialization operations such that the computingdevice enters a runtime environment, an Operating System (OS) engine inthe computing device may then claim the subset of the memory space thatwas previously reserved by the initialization data bucket forinitialization data, and store runtime data in that subset of the memoryspace during runtime operations. As will be appreciated by one of skillin the art in possession of the present disclosure, the use of theinitialization data bucket during initialization operations as describedherein confines any fragmentation that results from the allocation anduse of the memory space by the initialization engines to the subset ofmemory space reserved by the initialization data bucket, thus increasingcomputing device performance by reducing the need to review relativelylarge amounts of available memory space to find a contiguous region ofthe memory space for allocation, and requiring relatively smaller numberof descriptors in a memory map to identify the memory space to the OSengine in a manner that prevents unexpected behavior with some OSengines that may be a result of, for example, limitations in their OSloader code.

The method 300 begins at block 302 where, during initializationoperations, a processing system defines an initialization data bucketthat reserves a contiguous subset of memory space provided by a memorysystem for initialization data. In an embodiment, at or prior to theblock 302, the computing device 200 may be powered on, booted, reset,and/otherwise initialized such that initialization operations for thecomputing device 200 begin. As will be appreciated by one of skill inthe art in possession of the present disclosure, in a specific example,some initialization operations for the computing device 200 may includea chipset in the processing system 204 executing initialization code(e.g., Basic Input/Output System (BIOS) code) stored on a SerialPeripheral Interface (SPI) flash memory device (not illustrated) inorder to provide a BIOS engine that operates to copy the BIOS code fromthe SPI flash memory device to the main memory system 206 (e.g., to aDRAM device), followed by one or more cores in a Central Processing Unit(CPU) in the processing system 204 executing the BIOS code that wascopied to the main memory system 204 to provide the BIOS engine thatperforms, along with firmware drivers, a variety of initializationoperations (e.g., Power On Self Test (POST), etc.) to initialize thecomputing device 200.

For example, FIGS. 4 and 5 illustrate how the processing system 204 mayoperate to provide one or more initialization engine(s) 400 and 500,respectively, that may include the BIOS engine and firmware driversdiscussed above, as well as any other subsystem that one of skill in theart in possession of the present disclosure would appreciate may beallocated memory space during initialization operations for use instoring initialization data. As will be appreciated by one of skill inthe art in possession of the present disclosure, the BIOS enginedescribed herein may be provided by a Unified Extensible FirmwareInterface (UEFI) engine that was created as a replacement for legacyBIOS systems and that defines a software interface between an operatingsystem and firmware in the computing device 204, and the firmwaredrivers may be UEFI drivers.

Thus, in an embodiment of block 302, the processing system 204 maydefine an initialization data bucket that reserves a contiguous subsetor range of memory space provided by a memory system in the computingdevice 200 for the storage of initialization data by the initializationengine(s) 400/500. For example, prior to the initialization of the mainmemory system 206, a Driver eXecution Environment (DXE) core in theprocessing system 204 may operate to define the initialization databucket by generating a memory map of the memory system including theinitialization data bucket that will be reserved for the storage ofinitialization data by the initialization engines. FIG. 4 illustrates anembodiment in which the optional HBM system 204 a discussed above withreference to FIG. 2 is not provided with the processing system 204, andthe processing system 204 has defined the initialization data bucket asa boot services data bucket 402 that reserves a contiguous subset orrange of memory space provided by the main memory system 206 in thecomputing device 200 for the storage of boot services data by theinitialization engine(s) 400. FIG. 5 illustrates an embodiment in whichthe optional HBM system 204 a discussed above with reference to FIG. 2is provided with the processing system 204, and the processing system204 has defined the initialization data bucket as a boot services databucket 502 that reserves a contiguous subset or range of memory spaceprovided by the HBM system 204 b in the computing device 200 for thestorage of boot services data by the initialization engine(s) 500. Aswill be appreciated by one of skill in the art in possession of thepresent disclosure, boot services data may include any data generatedand stored by a BIOS engine and/or firmware drivers during “bootservices” that are defined by the UEFI specification and that areavailable when firmware “owns” the computing device platform. However,while specific initialization data is described, one of skill in the artin possession of the present disclosure will appreciate that otherinitialization data may fall within the scope of the present disclosureas well.

Referring now to FIGS. 6A and 6B, a memory system 600 is illustratedthat may be provided by the main memory system 206 or the HBM system 204a discussed above with reference to FIG. 2, and that is associated witha memory space 602. FIG. 6A illustrates how the boot services databuckets 402 or 502 may be defined by the processing system 204 at block302 such that the boot services data bucket 402 or 502 provides an“edge” of the memory space 602 provided by the memory system 600 (e.g.,a range of the memory space that starts with the first memory blockdescribed by the memory space 602), which results in the remainder 604of the memory space being provided by a contiguous subset of the memoryspace 602 that is located adjacent the boot services data bucket 402 or502 (e.g., “below” that boot services data bucket in FIG. 6A.)Similarly, FIG. 6B illustrates how the boot services data buckets 402 or502 may be defined by the processing system 204 at block 302 such thatthe boot services data bucket 402 or 502 provides an “edge” of thememory space 602 provided by the memory system 600 (e.g., a range of thememory space that ends with the last memory block described by thememory space 602), which results in the remainder 606 of the memoryspace being provided by a contiguous subset of the memory space 602 thatis located adjacent the boot services data bucket 402 or 502 (e.g.,“above” that boot services data bucket in FIG. 6A.) One of skill in theart in possession of the present disclosure will appreciate that theexamples illustrated in FIGS. 6A and 6B define the boot services bucketin a contiguous region or range (e.g., adjacent the “top” or “bottom”)of the memory space 602 in order to provide the largest possibleremaining subset of memory space that is contiguous, which may bebeneficial for subsystems that require relatively large memoryallocations (e.g., LINUX® OS loaders that utilize approximately 2 GB ofmemory during initialization of the computing device.) However, otherlocations for the boot services data bucket in the memory space may beutilized (e.g., in the “middle” of the memory space) if it is known thatthe remaining subsets of contiguous memory space are sufficient for theneeds of the subsystems that will utilize that memory space duringinitialization operations.

The method 300 then proceeds to block 304 where, during initializationoperations, an initialization engine provided by the processing systemallocates a portion of the contiguous subset of the memory spacereserved by the initialization data bucket for initialization data. Inan embodiment, at block 304, any of the initialization engines 400 or500 may operate during the initialization operations to allocate aportion of the contiguous subset or range of the memory space reservedby the boot services data bucket 402 or 502, respectively. For example,while the computing device 200 is in an initialization environment, theBIOS engine, firmware driver(s), or other initialization engine(s) 400or 500 may operate to allocate respective portions of the contiguoussubset of the memory space reserved by the boot services data buckets402 or 502 for use in storing initialization data utilized by the BIOSengine, firmware driver(s), or other initialization engine(s) 400 or500. As such, in some embodiments and following block 304, each of theinitialization engines 400 or 500 may be allocated a portion of thesubset of memory space that is reserved by the initialization/bootservices data bucket 402 or 502, respectively.

As will be appreciated by one of skill in the art in possession of thepresent disclosure, a relatively large number of firmware drivers orother initialization engines may be loaded while the computing device200 is in the runtime environment, which can result in the allocation ofa relatively large amount (and in some cases, all) of the subset of thememory space that is reserved by the initialization/boot services databucket. In some embodiments, in the event that all of the subset of thememory space that is reserved by the initialization data bucket 402 or502 is allocated to initialization engines 400 or 500, additionalinitialization engines (e.g., firmware drivers) that require memoryspace allocation may then begin to allocation portions of the memoryspace that is not reserved by the initialization data bucket.Furthermore, in the event that the allocation of the subset of thememory space that is reserved by the initialization data bucket 402 or502 to initialization engines 400 or 500 results in the initializationdata bucket not including any contiguous memory space that is sufficientfor an initialization engines' memory allocation requirement, additionalinitialization engines (e.g., firmware drivers) that require memoryspace allocation may then begin to allocation portions of the memoryspace that is not reserved by the initialization data bucket. While afew specific examples are provided, one of skill in the art inpossession of the present disclosure will appreciate that otherscenarios that require an initialization engine to allocate itselfmemory space outside of the subset of memory space reserved by theinitialization data bucket will fall within the scope of the presentdisclosure as well.

The method 300 then proceeds to block 306 where, during initializationoperations, the initialization engine provided by the processing systemstores initialization data in the portion of the contiguous subset ofthe memory space reserved by the initialization data bucket forinitialization data. In an embodiment, at block 306, each of theinitialization engines 400 or 500 that were allocated a portion of thesubset of memory space reserved by the initialization/boot service databucket 402 or 502, respectively, may operate to perform initializationoperations that include the storage of initialization/boot services datain their respective portion of the subset of memory space reserved bythe initialization/boot service data bucket 402 or 502. 00. For example,FIG. 7 illustrates each of the initialization engines 400 performingstorage operations 700 during the initialization of the computing device200 in order to store data in its respectively allocated portion of thesubset of the memory space reserved by the boot services data bucket 402defined in the main memory system 206. In another example, FIG. 8illustrates each of the initialization engines 500 performing storageoperations 800 during the initialization of the computing device 200 inorder to store data in its respective allocated portion of the subset ofthe memory space reserved by the boot services data bucket 402 definedin the HBM system 204 b.

As such, as will be appreciated by one of skill in the art in possessionof the present disclosure, the initialization engines 400 or 500 mayoperate to utilize memory blocks in their respective portions of thesubset of memory space reserved by the initialization/boot service databucket 402 or 502, release some of those memory blocks for use by otherinitialization engines, and/or perform a variety of other operationsthat result in fragmentation of the subset of memory space reserved bythe initialization/boot service data bucket 402 or 502, but thatfragmentation is generally limited to the subset of memory spacereserved by the initialization/boot service data bucket 402 or 502(e.g., that fragmentation may be completely limited to the subset ofmemory space reserved by the initialization/boot service data bucketwhen only that subset of memory space reserved by theinitialization/boot service data bucket is allocated to initializationengines, or that fragmentation may be primarily limited to the subset ofmemory space reserved by the initialization/boot service data bucketwhen portions of the memory space outside that subset of memory spacereserved by the initialization/boot service data bucket are allocated tosome initialization engines.)

The method 300 then proceeds to block 308 where, during runtimeoperations, a runtime engine provided by the processing system claimsthe contiguous subset of the memory space reserved by the initializationdata bucket for runtime data. In an embodiment, during or prior to block308, the initialization operations for the computing device 200 may becompleted, and the computing device 200 may enter a runtime environmentin which the processing system operates to provide a runtime engine. Forexample, FIG. 9 illustrates how, subsequent to the initialization of thecomputing device 200, the processing system 204 may operate to executeinstructions (e.g., included on the main memory system 206) to providean operating system engine 900. Similarly, FIG. 10 illustrates how,subsequent to the initialization of the computing device 200, theprocessing system 204 may operate to execute instructions (e.g.,included on the main memory system 206) to provide an operating systemengine 1000.

In an embodiment, upon provisioning of the operating system engine 900or 1000, a DXE core included in the processing system 204 may operate toreport the contiguous region or range of the memory space defined by theinitialization data bucket to the OS engine 900 or 1000. For example,FIG. 9 illustrates how the DXE core in the processing system 204 mayprovide an initialization engine 400 (e.g., the BIOS engine discussedabove) to perform reporting operations 902 that operate to report thecontiguous subset of the memory space reserved by the boot servicesbucket 402 to the OS engine 900, and FIG. 10 illustrates how the DXEcore in the processing system 204 may provide an initialization engine500 (e.g., the BIOS engine discussed above) to perform reportingoperations 1002 that operate to report the contiguous subset of thememory space reserved by the boot services bucket 502 to the OS engine1000 (e.g., in response to an OS loader calling“EFI_BOOT_SERVICES.GetMemoryMap( )” to retrieve a memory map.) As willbe appreciated by one of skill in the art in possession of the presentdisclosure, while the allocation of portions of the subset of memoryspace reserved by the boot services buckets 402 or 500 may be fragmentedfrom the point of view of the BIOS engine, the reporting of thecontiguous subset of the memory space reserved by the boot servicesbucket 402 or 502 eliminates the need to use a relatively large numberof descriptors in a memory map to identify the memory space to the OSengine, and thus the possibility of unexpected behavior with some OSengines that may result from limitations in their OS loader code iseliminated.

Following the reporting of the subset of the memory space reserved bythe initialization data bucket at block 308, the runtime engine mayoperate to claim that subset of the memory space for use in storingruntime data during runtime operations. As will be appreciated by one ofskill in the art in possession of the present disclosure, the memoryspace utilized for Boot Services Data may be utilized by the OS engineonce the OS engine takes control of the system memory (e.g., the OSengine may use the memory region previously marked by the BIOS as BootServices Data in order to load its kernel image.) As such, at block 308,the runtime engine may operate to perform a variety of operations thatone of skill in the art in possession of the present disclosure wouldrecognize as operating to claim the subset of the memory space reservedby the initialization data bucket. As such, FIG. 11 illustrates the OSengine 900 having claimed the subset of the memory space in the mainmemory system 206 that was reserved by the boot services data bucket402, and FIG. 12 illustrates the OS engine 1000 having claimed thesubset of the memory space in the HBM system 204 a that was reserved bythe boot services data bucket 502. However, while the OS engines aredescribed as claiming the subset of the memory space reserved by theinitialization data bucket, other runtime subsystems may claim thesubset of the memory space reserved by the initialization data bucketwhile remaining within the scope of the present disclosure as well. Themethod 300 then proceeds to block 310 where, during the runtimeoperations, the runtime engine provided by the processing system storesruntime data in at least a portion of the contiguous subset of thememory space. In an embodiment, at block 310, the OS engine 900 mayoperate to store runtime data in the subset of the memory space in themain memory system 206 that was previously reserved by the boot servicesdata bucket 402, and the OS engine 1000 may operate to store runtimedata in the subset of the memory space in the HBM system 204 a that waspreviously reserved by the boot services data bucket 502.

Thus, systems and methods have been described that provide for thecreation of a boot services data bucket that reserves a subset of thememory space provided by a memory system in a computing device for bootservices data, and then the allocation of portions of that subset of thememory space for BIOS engines and firmware drivers in the computingdevice, and the use of those portions of that subset of the memory spaceby the BIOS engines and firmware drivers for which they were allocatedin order to store boot services data during boot operations. Upon thecompletion of the boot operations such that the computing device entersa runtime environment, an Operating System (OS) engine in the computingdevice may then claim the subset of the memory space that was reservedby the boot services data bucket for runtime data, and store runtimedata in that subset of the memory space during runtime operations. Aswill be appreciated by one of skill in the art in possession of thepresent disclosure, the use of the boot services data bucket during bootoperations as described herein confines any fragmentation that resultsfrom the allocation and use of the memory space by the BIOS engines andfirmware drivers to the subset of memory space reserved by the bootservices data bucket, thus increasing computing device performance byreducing the need to review relatively large amounts of available memoryspace to find a contiguous region of the memory space for allocation,and requiring relatively smaller number of descriptors in a memory mapto identify the memory space to the OS engine in a manner that preventsunexpected behavior with some OS engines that may result from, forexample, limitations in their OS loader code.

Although illustrative embodiments have been shown and described, a widerange of modification, change and substitution is contemplated in theforegoing disclosure and in some instances, some features of theembodiments may be employed without a corresponding use of otherfeatures. Accordingly, it is appropriate that the appended claims beconstrued broadly and in a manner consistent with the scope of theembodiments disclosed herein.

What is claimed is:
 1. An initialization data memory space allocationsystem, comprising: a memory system having a memory space that includesan initialization data bucket that reserves a contiguous subset of thememory space for initialization data; and at least one initializationengine that is coupled to the memory system, wherein each initializationengine is configured, during initialization operations, to: allocate,for that initialization engine, a portion of the contiguous subset ofthe memory space reserved by the initialization data bucket; and storeinitialization data in that portion of the contiguous subset of thememory space reserved by the initialization data bucket; and a runtimeengine that is coupled to the memory system and that is configured,during runtime operations, to: claim the contiguous subset of the memoryspace reserved for initialization data by the initialization data bucketfor runtime data; and store runtime data in at least a portion of thecontiguous subset of the memory space.
 2. The system of claim 1, whereinthe initialization data bucket that reserves the contiguous subset ofthe memory space for the initialization data is a boot services databucket that reserves the contiguous subset of the memory space for bootservices data.
 3. The system of claim 1, wherein the memory system isprovided by a main memory system including Dynamic Random Access Memory(DRAM) devices.
 4. The system of claim 1, wherein the memory system isprovided by a High Bandwidth Memory (HBM) system included with aprocessing system that is configured to provide the at least oneinitialization engine and the runtime engine.
 5. The system of claim 1,wherein the at least one initialization engine includes a BasicInput/Output System (BIOS) engine and at least one firmware driverengine.
 6. The system of claim 1, wherein the at least oneinitialization engine is configured to: report, to the runtime engine,the contiguous subset of the memory space reserved by the initializationdata bucket.
 7. An Information Handling System (IHS), comprising: aprocessing system that is configured to: define an initialization databucket that reserves a contiguous subset of a memory space provided by amemory system for initialization data; and execute instructions to causethe processing system to provide: at least one initialization engine,wherein each initialization engine is configured, during initializationoperations, to: allocate, for that initialization engine, a portion ofthe contiguous subset of the memory space reserved by the initializationdata bucket; and store initialization data in that portion of thecontiguous subset of the memory space reserved by the initializationdata bucket; and a runtime engine that is coupled to the memory systemand that is configured, during runtime operations, to: claim thecontiguous subset of the memory space reserved for initialization databy the initialization data bucket for runtime data; and store runtimedata in at least a portion of the contiguous subset of the memory space.8. The IHS of claim 7, wherein the initialization data bucket thatreserves the contiguous subset of the memory space for theinitialization data is a boot services data bucket that reserves thecontiguous subset of the memory space for boot services data.
 9. The IHSof claim 7, wherein the memory system is provided by a main memorysystem that is coupled to the processing system and that includesDynamic Random Access Memory (DRAM) devices.
 10. The IHS of claim 7,wherein the memory system is provided by a High Bandwidth Memory (HBM)system included with the processing system.
 11. The IHS of claim 7,wherein the at least one initialization engine includes a BasicInput/Output System (BIOS) engine and at least one firmware driverengine.
 12. The IHS of claim 7, wherein processing system is configuredto: report, to the runtime engine, the contiguous subset of the memoryspace reserved by the initialization data bucket.
 13. The IHS of claim7, wherein processing system is configured to: define the initializationdata bucket that reserves the contiguous subset of the memory spaceprovided by the memory system such that the initialization data bucketprovides an edge of the memory space provided by the memory system. 14.A method for allocating memory space for initialization data,comprising: defining, by a processing system during initializationoperations, an initialization data bucket that reserves a contiguoussubset of a memory space provided by a memory system for initializationdata; allocating, by an initialization engine provided by the processingsystem for that initialization engine during the initializationoperations, a portion of the contiguous subset of the memory spacereserved by the initialization data bucket; storing, by theinitialization engine provided by the processing system during theinitialization operations, initialization data in the portion of thecontiguous subset of the memory space reserved by the initializationdata bucket; claiming, by a runtime engine provided by the processingsystem during runtime operations, the contiguous subset of the memoryspace reserved for initialization data by the initialization data bucketfor runtime data; and storing, by the runtime engine provided by theprocessing system during the runtime operations, runtime data in atleast a portion of the contiguous subset of the memory space.
 15. Themethod of claim 14, wherein the initialization data bucket that reservesthe contiguous subset of the memory space for the initialization data isa boot services data bucket that reserves the contiguous subset of thememory space for boot services data.
 16. The method of claim 14, whereinthe memory system is provided by a main memory system that is coupled tothe processing system and that includes Dynamic Random Access Memory(DRAM) devices.
 17. The method of claim 14, wherein the memory system isprovided by a High Bandwidth Memory (HBM) system included with theprocessing system.
 18. The method of claim 14, wherein theinitialization engine includes one of a Basic Input/Output System (BIOS)engine or at least one firmware driver engine.
 19. The method of claim14, further comprising: reporting, by the processing system to theruntime engine, the contiguous subset of the memory space reserved bythe initialization data bucket.
 20. The method of claim 14, furthercomprising: defining, by the processing system, the initialization databucket that reserves the contiguous subset of the memory space providedby the memory system such that the initialization data bucket providesan edge of the memory space provided by the memory system.